HotDog Version 2.53 =================== Changes from 2.52 ----------------- ROVER has been changed and can now see the World Wide Web ! Click on your http:// links and you're cruising the web. The Table editor has been beefed up and can now handle cell contents with HTML wrapped around them. Word wrap method tweaked, may help with the "GPF when pasting" bug. Major Things To Watch For ========================= This program can run either as HotDog Standard or HotDog Pro (if it's still unregistered or has an evaluation extension key). Once you enter the serial number for Pro or Standard it will only run in that mode, until you give it a new serial number. See the Help/Register HotDog menu option for the switch that toggles between the two modes. During installation HotDog 2.53 (and 2.5 and 2.51 for that matter) tries to find your old \windows\htdogpro.ini file and copy your old registration details into the new \%HotDogDirectory%\HOTDOG.INI file, so you won't have to worry about transfering the serial number into it. But if something goes wrong here's what HotDog looks for : [Registration Details] User Name=Your Name Here Company Name=Your Company Here Serial Number=ATwentyCharacterCode BUT !!!! If you've got an extension of your evaluation the date should be appended to the Serial Number, like so: Serial Number=ATwentyCharacterCode30-Apr-96 If the self-registering screen doesn't correctly parse the information we send to you then you can go directly to HOTDOG.INI in the HotDog directory (not in the windows directory) and type it in. KNOWN BUGS ========== HotFTP should work, but if it doesn't then we can only tell you that we're re-writing it right now. Try looking a several different sites to try and find the characteristics of those that HotFTP won't talk to. We have had reports of the cursor rapidly changing from the normal pointer to an hourglass, and back again, and of HotDog just locking up. We can't as yet reproduce this, so more information would be helpful. GPFs in HighEdit (hevb.vbx, hevb.dll) and ImageKnife (IKENG16.DLL) can occur on some systems. Again, it seems to be a system-specific fault - these files won't play nicely with some other file already in your \windows\system directory but, again since we can't reproduce it, we don't know which ones they are. If you find out please tell us ! :)